Prioritizing smart tag creation

ABSTRACT

An aspect provides a method, including: accessing, using a processor, a store of historical user object event information; building, using the processor, a tagging profile based on the store of historical user object event information; determining, using the processor, a new user object event; and determining, using the processor, a priority for tag generation for the new object event using the tagging profile. Other aspects are described and claimed.

BACKGROUND

Information handling devices (“devices”) come in a variety of forms, forexample laptop computing devices, tablet computing devices, smartphones, e-readers, MP3 players, and the like. Such devices areconfigured for media consumption and users typically store “files”,e.g., music, videos, pictures, documents, etc. (hereinafter simply“objects”) on the devices.

For example, a typical device user may have thousands and thousands ofobjects (files, pictures, content, etc.) scattered across his or herdevice. To compound this, with the advent of cloud computing and remotestorage, a user may have objects scattered across many devices (e.g.,laptop, tablet, smart phone, work station, etc.) and in cloud storagedevice(s). The user might remember some things about an object he or shewishes to retrieve, but the user nevertheless often may find itdifficult to find it quickly. For example, many devices create mediafile names that are less than helpful (e.g., a number corresponding to adigital image captured by a smart phone and stored on the smart phonelocally and in a cloud or other network connected device). Even if theuser has chosen a memorable file name or storage folder, objectretrieval can prove challenging in the current use environment wheretypically the objects are scattered throughout the device and/or devicesand not well organized from a retrieval standpoint.

BRIEF SUMMARY

In summary, one aspect provides a method, comprising: accessing, using aprocessor, a store of historical user object event information;building, using the processor, a tagging profile based on the store ofhistorical user object event information; determining, using theprocessor, a new user object event; and determining, using theprocessor, a priority for tag generation for the new object event usingthe tagging profile.

Another aspect provides an information handling device, comprising: aprocessor; a memory device that stores instructions accessible to theprocessor, the instructions being executable by the processor to: accessa store of historical user object event information; building a taggingprofile based on the store of historical user object event information;determine a new user object event; and determine a priority for taggeneration for the new object event using the tagging profile.

A further aspect provides a product, comprising: a storage device havingcode stored therewith, the code comprising: code that accesses a storeof historical user object event information; code that builds a taggingprofile based on the store of historical user object event information;code that determines a new user object event; and code that determines apriority for tag generation for the new object event using the taggingprofile.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of information handling device circuitry.

FIG. 2 illustrates another example of information handling devicecircuitry.

FIG. 3 illustrates an example method of prioritizing smart tag creation.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearance of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well knownstructures, materials, or operations are not shown or described indetail to avoid obfuscation.

As described in further detail herein, a user is often faced with aserious challenge when attempting to find an object he or she wants, andit is often doubly challenging to find the object quickly. Such a userwould benefit greatly from a retrieval mechanism that operates on theprinciple of tagging objects with data regarding “some thing(s) you willremember a year or more later”.

Today users are limited in their object retrieval choices. For instance,users are basically limited to only searching by file name and/or datethat file was modified, and/or information inside the file for some typeof files (e.g., words contained within a Microsoft WORD document).Unfortunately, from a usability stand point, this is either entirelyineffective (e.g., file name on a video file is a machine generatednumber) or simply frustrating, as this is not the way our minds work toremember clues about the object (and that are not necessarily in theobject), especially if it is a non-data object (picture, video, etc.).

Accordingly, an embodiment provides the ability to use smart tags (alsoreferred to herein simply as “tags”) for retrieval of user generatedobjects (e.g., pictures, documents, files, etc.) that are stored on theuser's device(s). Some useful information regarding smart tags is foundin co-pending and commonly assigned U.S. patent application Ser. No.13/919,293, entitled “SMART TAGS FOR CONTENT RETRIEVAL”, filed on Jun.17, 2013 and in co-pending and commonly assigned U.S. patent applicationSer. No. 13/919,376, entitled “CONTEXTUAL SMART TAGS FOR CONTENTRETRIEVAL”, filed on Jun. 17, 2013; the contents of each of these priorapplications are incorporated by reference in their entirety herein.

An embodiment permits, for example, generation of a smart tag describingan object (e.g., a picture file, a document, etc.) based on an objectevent, e.g., information relating to an object created by a user andstored on one of the user's devices. Thus, a user creating a picturefile by taking a picture may have a smart tag created and associatedtherewith and stored in a tag collection, e.g., on the user deviceand/or in a remote or cloud storage device. The tag may containmetadata, e.g., user provided metadata such as audio for generating keywords describing the picture file, and/or system originated data, e.g.,from one or more sensors, such as global positioning data regarding thelocation the picture was taken, data indicating an association of suchposition with nearby businesses or landmarks as for example available inmap data, sensed user devices in the location of the user deviceutilized to take the picture, e.g., smart phones of friends or familymembers in the vicinity, etc., data from sensors or other informationrepositories regarding the environment, e.g., temperature, weatherevents, ambient light, timing data, etc.

Given the ability to generate such smart tags, a user may be assisted ina search for an object via leveraging the smart tag data in the search.For example, if a user happens to be taking pictures of a friend at aparticular occasion, e.g., Bob's 50th birthday party, the user couldsimply say “Bob's 50th birthday party” to provide speech input forcreating a smart tag for the object to be created, i.e., the picture.This information is then processed (e.g., converted using aspeech-to-text mechanism) and stored as a separate tag or tags with alink/naming convention linking it to the object (picture). The user maythen later retrieve the object, i.e., the picture in this example,simply by inputting a search such as “the picture I took at the birthdayparty last week” and searching the smart tags for this object.

Tagging the entire content universe of a user (e.g., creating smarttag(s) including all key words contained within a word processingdocument, for each such document and all other objects, as well ascreating other smart tags to capture contextual data, etc.), however,might take a very long time, might consume a large amount of storage,and/or might introduce a time lag for pushing the smart tags intostorage, e.g., onto a cloud based storage system. This might cause adelay in query responses or diminished quality of the query responses,unwanted utilization of device resources, etc.

Accordingly, an embodiment takes into account user preferences and/orbehaviors when smart tags for content are discovered or created. Thisfacilitates an intelligent smart tag generation process for tagging thecontent/objects of the user or group of associated users, as furtherdescribed herein.

An embodiment creates a tagging profile for a user, e.g., via analyzinga query history and/or user feedback regarding query results. A taggingprofile may comprise types of content that the user was previouslyinterested in (e.g., word processing documents, calendar entries, etc.)and/or a list of tag categories that is/are relevant, e.g., based onpast usage thereof. Thus, an embodiment facilitates user-specific andgroup specific tagging profiles such that smart tags may be efficientlygenerated, stored, and/or made accessible to users withoutover-processing user content or over burdening the user's devices.

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to smart phone and/or tabletcircuitry 100, an example illustrated in FIG. 1 includes a system on achip design found for example in tablet or other mobile computingplatforms. Software and processor(s) are combined in a single chip 110.Processors comprise internal arithmetic units, registers, cache memory,busses, I/O ports, etc., as is well known in the art. Internal bussesand the like depend on different vendors, but essentially all theperipheral devices (120) may attach to a single chip 110. The circuitry100 combines the processor, memory control, and I/O controller hub allinto a single chip 110. Also, systems 100 of this type do not typicallyuse SATA or PCI or LPC. Common interfaces, for example, include SDIO andI2C.

There are power management chip(s) 130, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 140, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 110, is usedto supply BIOS like functionality and DRAM memory.

System 100 typically includes one or more of a WWAN transceiver 150 anda WLAN transceiver 160 for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additionally devices 120 are commonly included. System 100 oftenincludes a touch screen 170 for data input and display/rendering. System100 also typically includes various memory devices, for example flashmemory 180 and SDRAM 190.

FIG. 2 depicts a block diagram of another example of informationhandling device circuits, circuitry or components. The example depictedin FIG. 2 may correspond to computing systems such as the THINKPADseries of personal computers sold by Lenovo (US) Inc. of Morrisville,N.C., or other devices. As is apparent from the description herein,embodiments may include other features or only some of the features ofthe example illustrated in FIG. 2.

The example of FIG. 2 includes a so-called chipset 210 (a group ofintegrated circuits, or chips, that work together, chipsets) with anarchitecture that may vary depending on manufacturer (for example,INTEL, AMD, ARM, etc.). INTEL is a registered trademark of IntelCorporation in the United States and other countries. AMD is aregistered trademark of Advanced Micro Devices, Inc. in the UnitedStates and other countries. ARM is an unregistered trademark of ARMHoldings plc in the United States and other countries. The architectureof the chipset 210 includes a core and memory control group 220 and anI/O controller hub 250 that exchanges information (for example, data,signals, commands, etc.) via a direct management interface (DMI) 242 ora link controller 244. In FIG. 2, the DMI 242 is a chip-to-chipinterface (sometimes referred to as being a link between a “northbridge”and a “southbridge”). The core and memory control group 220 include oneor more processors 222 (for example, single or multi-core) and a memorycontroller hub 226 that exchange information via a front side bus (FSB)224; noting that components of the group 220 may be integrated in a chipthat supplants the conventional “northbridge” style architecture. One ormore processors 222 comprise internal arithmetic units, registers, cachememory, busses, I/O ports, etc., as is well known in the art.

In FIG. 2, the memory controller hub 226 interfaces with memory 240 (forexample, to provide support for a type of RAM that may be referred to as“system memory” or “memory”). The memory controller hub 226 furtherincludes a LVDS interface 232 for a display device 292 (for example, aCRT, a flat panel, touch screen, etc.). A block 238 includes sometechnologies that may be supported via the LVDS interface 232 (forexample, serial digital video, HDMI/DVI, display port). The memorycontroller hub 226 also includes a PCI-express interface (PCI-E) 234that may support discrete graphics 236.

In FIG. 2, the I/O hub controller 250 includes a SATA interface 251 (forexample, for HDDs, SDDs, etc., 280), a PCI-E interface 252 (for example,for wireless connections 282), a USB interface 253 (for example, fordevices 284 such as a digitizer, keyboard, mice, cameras, phones,microphones, storage, other connected devices, etc.), a networkinterface 254 (for example, LAN), a GPIO interface 255, a LPC interface270 (for ASICs 271, a TPM 272, a super I/O 273, a firmware hub 274, BIOSsupport 275 as well as various types of memory 276 such as ROM 277,Flash 278, and NVRAM 279), a power management interface 261, a clockgenerator interface 262, an audio interface 263 (for example, forspeakers 294), a TCO interface 264, a system management bus interface265, and SPI Flash 266, which can include BIOS 268 and boot code 290.The I/O hub controller 250 may include gigabit Ethernet support.

The system, upon power on, may be configured to execute boot code 290for the BIOS 268, as stored within the SPI Flash 266, and thereafterprocesses data under the control of one or more operating systems andapplication software (for example, stored in system memory 240). Anoperating system may be stored in any of a variety of locations andaccessed, for example, according to instructions of the BIOS 268. Asdescribed herein, a device may include fewer or more features than shownin the system of FIG. 2.

Information handling device circuitry, as for example outlined in FIG. 1or FIG. 2, may be user devices that are used to create and/or storeobjects, e.g., data or files created or consumed by the user. Forexample, devices including circuitry outlined in the example of FIG. 1may include a smart phone with which a user takes pictures, takesvideos, purchases and downloads music files, sends emails, texts, etc.Each of these data objects or files (simply referred to herein as“objects” or “user objects”) may be stored by the user, e.g., on thedevice, in the cloud, on multiple user devices, etc.

As outlined above, a user will often face a significant challenge whenhe or she later attempts to find a particular object of interest. Thischallenge comes from the sheer volume of objects which may be created orgenerated and stored by the user.

For example, a user may wish to find a file that he or she worked onlast week. This may include hundreds of such documents (e.g., wordprocessing documents). Furthermore, if the user is defined as a group ofusers (e.g., working group, company division, social club, etc.), thelist of documents worked on within the last week, month, etc. may growexponentially.

Embodiments provide for smart tags to be created, thus simplifying thesearching and location of such objects, e.g., using parameters orcharacteristics of interest to the user and thus easily remember. Forexample, the user may recall that he or she not only worked on adocument last week, but also that he or she worked on that document at acoffee shop and that was a day it snowed. These additional parameters orcharacteristics regarding object context are captured in the smart tagsand may be leveraged for object retrieval.

Given the large amount of such context data that may be generated andused in forming the smart tags, an embodiment facilitates an efficientcreation or generation process. This allows an embodiment tointelligently prioritize which smart tags are created for an object.

Referring to FIG. 3, for example, at an appropriate time, e.g., when auser creates an object or prior to object creation, an embodiment mayaccess object search information at 301. This object search informationmay include historical object searching information of a particularuser, a group of users, etc. The object search information may be storedon the user's device, partly on the user's device and partly on anotherdevice, or entirely on another device, e.g., a cloud based storagelocation.

In any event, an embodiment may utilize the object search information toform or build a tagging profile at 302. That is, an embodiment maydetect various characteristics captured in or represented by the objectsearch information to profile a particular user, a particular group ofusers etc. This information may therefore be utilized to build a taggingprofile at 302.

For example, an embodiment may analyze a user's query history and/or theuser's feedback about the results of queries to extract data useful informing the tagging profile at 302. By way of example, the taggingprofile may include the types of content that the user was previouslyinterested in, as indicated in the object search information, e.g., wordprocessing documents, calendar entries, etc. The tagging profile mayinclude a list of smart tag categories that are relevant to the user,e.g., as indicated by the past usage thereof in completing searches forthis particular user, e.g., environmental conditions during objectcreation/modification, etc. The tagging profile may include a set ofsmart tags that have been relevant in the past to the user, e.g.,specific smart tags/categories used by the user.

With a tagging profile available, when the user next creates an object,e.g., as determined at 303, an embodiment may prioritize the order inwhich smart tags are generated for the object using the tagging profileat 304. Thus, a user taking a picture, for example, may have indicatedin his or her tagging profile that these objects are often searched forusing a location smart tag category, e.g., location where picture wastaken. Thus, an embodiment may prioritize a location tag category as apriority category, whereas other smart tag categories, e.g.,temperature, weather, time, participants, etc., may be determined to belower priority smart tag categories.

Given this, an embodiment may first create location smart tags of thelocation smart tag category at 305, e.g., GPS location smart tag, nearbybusiness smart tags, general geographic location smart tags, etc. Thisfacilitates generating the smart tags of a category or categoriesinferred to be most important to the user according to some metric,e.g., a frequency metric included in the tagging profile. An embodimentmay nonetheless generate additional smart tags at 305, even if thesetags are associated with lower priority categories, e.g., other userdevices detected nearby, timing information, etc. These lower prioritycategory smart tags may be created and stored, transmitted (e.g., tocloud storage), etc., as a background process. For example, if the userhas not created an object, e.g., as determined at 303, an embodiment maynonetheless proceed or continue to create, store, organize, transmit,etc., smart tags for previously created objects. Thus, a full set ofsmart tags may still be generated by an embodiment, but an embodimentintelligently prioritizes smart tag creation, storage, transmission,etc. using a tagging profile of the user or group in question.

The tagging infrastructure may therefore tag content using differentprocesses, e.g., a real-time process to tag what the user is working onright now (e.g., a freshly created object) and a background process thatwill tag existing content items without the user needing to interactwith the system. The tagging infrastructure may use the tagging profilebuilt at 302 to focus the real-time tagging process on the smarttags/tag categories identified as priorities in the tagging profile. Thebackground tagging process may still collect the full set of smart tags,but it will give higher priority to the content items that are of therelevant content types of the tagging profile.

By way of example, a sales representative may work more with a calendarapplication and an email application than with a word processingapplication. An embodiment therefore may utilize a tagging profile forthe sales representative in which it is indicated that objects of thesales representative's favorite applications should be the primary focusfor generating smart tags, e.g., application specific smart tags. Itwill be appreciated that the tagging profile may be formed,supplemented, updated, etc., according to other like or similar users,e.g., as facilitated by sharing tagging profile attributes among users.Moreover, group tagging profiles for similar or like users may be formedand refined over time such that a user may have a tagging profile builtfor him or her using group tag usage/behaviors.

The tagging profile thus may be created by analyzing a user's pastsearch queries, the result of such queries, and the items the userpreferred in the results. Based on this analysis, it is possible toextract which content types were most relevant for the user in the past.This process may include for example ranking of content types byrelevance for the user or group of users.

By applying feature extraction, it is possible to extract a set of smarttags and smart tag categories from the object search information thatwere most significant in generating the search results for the user. Forexample, a user might usually search for files by filename and keywords,but never by author. This may result in a tagging profile for thisspecific user (across devices) which prioritizes file name smart tagsand keyword smart tags but not author smart tags. Since tastes andpreferences of users may change over time, the tagging profile may berecalculated (e.g., continuously, according to a timing policy, etc.) asthe user or group of users is/are using the system.

Calculation of the tagging profile need not suffer from a“cold-start-problem”, were in the beginning of an interaction with auser, a system has not collected enough data to calculate an accuratetagging profile. For example, a default tagging profile may be used forsuch a new user or the user could be classified within known groups ofusers for which a reasonable default tagging profile is known. Thus, thebasis for defining the tag priorities may include a priori rules and/orpredefined queries. An embodiment may for example use sample data toseed a database to derive a default priority profile.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device that are executed by aprocessor. Any combination of one or more non-signal device readablestorage medium(s) may be utilized. A storage medium may be, for example,an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples of a storage medium wouldinclude the following: a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a storage medium is not asignal and “non-transitory” includes all media except signal media.

Program code embodied on a storage medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, et cetera, or any suitable combination of theforegoing.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made through other devices (for example, throughthe Internet using an Internet Service Provider), through wirelessconnections, e.g., near-field communication, or through a hard wireconnection, such as over a USB connection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products accordingto various example embodiments. It will be understood that the actionsand functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a general purpose information handling device, a special purposeinformation handling device, or other programmable data processingdevice to produce a machine, such that the instructions, which executevia a processor of the device implement the functions/acts specified.

It is worth noting that while specific blocks are used in the figures,and a particular ordering of blocks has been illustrated, these arenon-limiting examples. In certain contexts, two or more blocks may becombined, a block may be split into two or more blocks, or certainblocks may be re-ordered or re-organized as appropriate, as the explicitillustrated examples are used only for descriptive purposes and are notto be construed as limiting.

As used herein, the singular “a” and “an” may be construed as includingthe plural “one or more” unless clearly indicated otherwise.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

What is claimed is:
 1. A method, comprising: accessing, using aprocessor, a store of historical user object event informationcomprising object search information associated with queries provided bya user during searches for stored objects; building, based upon theobject search information, a tagging profile for the user using thestore of historical user object event information, wherein the taggingprofile identifies at least one tag category to be associated with theuser based upon content identified from the object search information;identifying creation of a new user object associated with the user; andgenerating at least one tag for the new user object, wherein thegenerated tag is identified using the tagging profile and prioritizingpossible tags for the new user object using the tagging profile.
 2. Themethod of claim 1, wherein the determination is based upon determining apriority tag category for tag generation and determining a lowerpriority tag category for later tag generation.
 3. The method of claim2, further comprising generating a tag associated with the priority tagcategory within a predetermined time of the new user object event. 4.The method of claim 3, further comprising thereafter generating a tagassociated with the lower priority tag category as a background process.5. The method of claim 1, wherein the tagging profile is user specific.6. The method of claim 5, wherein the tagging profile indicates tagcategories frequently used by the user.
 7. The method of claim 1,wherein the tagging profile is group specific.
 8. The method of claim 7,wherein the tagging profile indicates tag categories frequently used bya group.
 9. The method of claim 7, wherein the group is associated viacloud account data with a user associated with the new object event. 10.The method of claim 1, wherein a user object is an object created by theuser and resident on one or more devices associated with the user. 11.An information handling device, comprising: a processor; a memory devicethat stores instructions accessible to the processor, the instructionsbeing executable by the processor to: access a store of historical userobject event information comprising object search information associatedwith queries provided by a user during searches for stored objects;build, based upon the object search information, a tagging profile forthe user using the store of historical user object event information,wherein the tagging profile identifies at least one tag category to beassociated with the user based upon content identified from the objectsearch information; identify creation of a new user object associatedwith the user; and generate at least one tag for the new user object,wherein the generated tag is identified using the tagging profile andprioritizing possible tags for the new user object using the taggingprofile.
 12. The information handling device of claim 11, wherein thedetermination is based upon determining a priority tag category for taggeneration and determining a lower priority tag category for later taggeneration.
 13. The information handling device of claim 12, wherein theinstructions are further executable by the processor to generate a tagassociated with the priority tag category within a predetermined time ofthe new user object event.
 14. The information handling device of claim13, wherein the instructions are further executable by the processor tothereafter generate a tag associated with the lower priority tagcategory as a background process.
 15. The information handling device ofclaim 11, wherein the tagging profile is user specific.
 16. Theinformation handling device of claim 15, wherein the tagging profileindicates tag categories frequently used by the user.
 17. Theinformation handling device of claim 11, wherein the tagging profile isgroup specific.
 18. The information handling device of claim 17, whereinthe tagging profile indicates tag categories frequently used by a group.19. The information handling device of claim 17, wherein the group isassociated via cloud account data with a user associated with the newobject event.
 20. A product, comprising: a non-signal storage mediumhaving processor executable code stored therewith, the code comprising:code that accesses a store of historical user object event informationcomprising object search information associated with queries provided bya user during searches for stored objects; code that builds based uponthe object search information a tagging profile for the user using thestore of historical user object event information, wherein the taggingprofile identifies at least one tag category to be associated with theuser based upon content identified from the object search information;code that identifies creation of a new user object associated with theuser; and code that generates at least one tag for the new user object,wherein the generated tag is identified using the tagging profile andprioritizing possible tags for the new user object using the taggingprofile.